Node types

Consolidates income statements from other nodes into a unified balance sheet. A model can only have one balance sheet node.

Used to reconcile inter-company activities across multiple nodes.

The Eliminations Node is a manual entry node used to offset eliminating entries between entities. The total dollars are entered for the other entities in other operations nodes. Then, a separate Eliminations Node is created using the Eliminations Node type. You can enter amounts for all years as needed for both income statement and balance sheet line items.

To create an eliminations node:

1. Follow the instructions in Creating a node, and in Step 2, select Eliminations as the node type.
2. When the new node opens, input data in the appropriate line items for the income statement and balance sheet.

Each entity node has its own revenues and expenses, and maintains its own balance sheet (for example, does not send its income statement to the Balance Sheet node).

Contains only expense data. If there are variable expenses, another node with the necessary driver must be mapped to it via the Control Panel to Manage Nodes dialog in the Fin Plan Admin task pane. This node type might be used to track expenses related to multiple service lines.

Uses the Health Plan template. Consolidates income statements from other health plan nodes into a unified balance sheet. A model can only have one balance sheet node.

Uses the Health Plan template. Each entity node has its own revenues and expenses, and maintains its own balance sheet (for example, does not send its income statement to the Balance Sheet node).

Uses the Health Plan template. Contains only expense data. If there are variable expenses, another node with the necessary driver must be mapped to it via the Control Panel to Manage Nodes dialog in the Fin Plan Admin task pane. This node type might be used to track expenses related to multiple service lines.

Uses the Health Plan template. Each operations node models a component of the organization with associated revenues and expenses (Acute, Psych, Rehab, and so on).

Uses the Health Plan template. Contains only revenue data. If revenue is variable, another node with the necessary driver must be mapped to it using the Control Panel to Manage Nodes dialog in the Fin Plan Admin task pane. This node type might be used to have revenue from multiple nodes drive a common set of expenses.

Tracks the volume, revenue, expense, capital spending, bad debt, and charity associated with a project. The project must begin in a future year (does not contain historical data) and contains a full balance sheet. This node also calculates the net present value and ROI.

Calculates the estimated costs for a bond issuance for a given cash outlay. This node assumes that an asset will be created and calculates depreciation, amortization, and so on. New Debt nodes are forward-looking and do not contain historical data. You also cannot change the Global set or the projection years for this type of node.

Contains operating revenue and expenses and excludes all patient level revenue and volume.

Each operations node models a component of the organization with associated revenues and expenses (Acute, Psych, Rehab, and so on).

Uses the Physician template. Consolidates income statements from other health plan nodes into a unified balance sheet. A model can only have one balance sheet node.

Uses the Physician template. Each entity node has its own revenues and expenses, and maintains its own balance sheet (for example, does not send its income statement to the Balance Sheet node).

Uses the Physician template. Contains only expense data. If there are variable expenses, another node with the necessary driver must be mapped to it via the Control Panel to Manage Nodes dialog in the Fin Plan Admin task pane. This node type might be used to track expenses related to multiple service lines.

Uses the Physician template. Each operations node models a component of the organization with associated revenues and expenses (Acute, Psych, Rehab, and so on).

Uses the Physician template. Contains only revenue data. If revenue is variable, another node with the necessary driver must be mapped to it using the Control Panel to Manage Nodes dialog in the Fin Plan Admin task pane. This node type might be used to have revenue from multiple nodes drive a common set of expenses.

Used to integrate projects from Capital Planning.

Uses the Research template. Consolidates income statements from other health plan nodes into a unified balance sheet. A model can only have one balance sheet node.

Uses the Researchtemplate. Each entity node has its own revenues and expenses, and maintains its own balance sheet (for example, does not send its income statement to the Balance Sheet node).

Uses the Research template. Contains only expense data. If there are variable expenses, another node with the necessary driver must be mapped to it via the Control Panel to Manage Nodes dialog in the Fin Plan Admin task pane. This node type might be used to track expenses related to multiple service lines.

Uses the Research template. Each operations node models a component of the organization with associated revenues and expenses (Acute, Psych, Rehab, and so on).

Contains only revenue data. If revenue is variable, another node with the necessary driver must be mapped to it using the Control Panel to Manage Nodes dialog in the Fin Plan Admin task pane. This node type might be used to have revenue from multiple nodes drive a common set of expenses.